System and method for transacting lead and scheduled appointment records

ABSTRACT

The present invention is generally a system and method for transacting lead records and scheduled appointment records concerning business opportunities in the real estate industry. The transactions may include offering the scheduled appointment records or lead records for sale, as well as auctioning the records. Several software modules may be provided to: receive, categorize, qualify, and distribute leads that mature into transactional opportunities; determine the geographic location of real estate client users and transactional opportunities near a user&#39;s location or selected region; facilitate management of each transactional opportunity by the client user; facilitate management of each transactional opportunity by the service provider; and various other functions and services consistent with the present system and method. Moreover, an exchange platform may be implemented with the present system whereby affiliates of the service provider may introduce their own leads and sell them to subscribers.

PRIORITY NOTICE

This application is a continuation of pending U.S. Non-provisionalapplication Ser. No. 15/899,306, filed on Feb. 19, 2018, which is acontinuation of U.S. Non-provisional application Ser. No. 15/097,568,filed on Apr. 13, 2016, which claims priority under 35 U.S.C. § 119(e)to U.S. Provisional Patent Application Ser. No. 62/272,429 filed on Dec.29, 2015, the disclosure of each incorporated herein by reference intheir entirety.

TECHNICAL FIELD OF THE INVENTION

The present invention relates in general to a system and method fortransacting lead and scheduled appointment records, and morespecifically, to a system and method for facilitating transactions ofscheduled appointments and leads concerning business opportunities inthe real estate industry.

COPYRIGHT AND TRADEMARK NOTICE

A portion of the disclosure of this patent application may containmaterial that is subject to copyright protection. The owner has noobjection to the facsimile reproduction by anyone of the patentdocuments or the patent disclosure, as it appears in the Patent andTrademark Office patent file or records, but otherwise reserves allcopyrights whatsoever.

Certain marks referenced herein may be common law or registeredtrademarks of third parties affiliated or unaffiliated with theapplicant or the assignee. Use of these marks is by way of example andshould not be construed as descriptive or to limit the scope of thisinvention to material associated only with such marks.

BACKGROUND OF THE INVENTION

Traditionally, purchasing real estate requires prospective buyers andsellers to transact through a real estate professional—typically alicensed individual or entity such as a licensed real estate agent,broker, or realtor—referred hereinafter simply as “realtor”. With anever growing real estate industry, the number of realtors has similarlyincreased. As such, realtors are finding that keeping a competitive edgeagainst the tremendous number of licensed individuals or entities isincreasingly difficult.

Realtors interested in pursuing business opportunities in the realestate industry face numerous challenges. With more professionalsavailable in a particular area, prospective buyers and prospectivesellers may choose from a plethora of available licensed professional tohelp them with real estate transactions. Moreover, the World Wide Webhas made the largest real estate companies and the more independentlicensed individuals, seemingly equally accessible. Hence, there is agrowing need for maintaining a competitive edge in the real estateindustry.

One of the challenges that realtors face is the procurement of newprospects and new business opportunities or leads. While the Internetmay make a realtor's contact information widely available to the public,receiving quality leads typically means having to spend considerableresources sifting through requests with low or no potential of turninginto a successful transaction. Similarly, the vast number of competingrealtors and flood of advertising information makes brandingincreasingly difficult. Furthermore, even where a good referral systemis implemented, turning those referrals into successful transactions andturning current business into repeat business remains a challenge.

Therefore, there are several challenges with the current state of thereal estate industry that have not been adequately addressed by theprior art. These challenges persist because a need to provide a systemand method for facilitating real estate transactions has not beenadequately met. As such, a new and improved system that facilitatestransacting business opportunities in the real estate industry isdesirable, and it is to these ends that the present invention has beendeveloped.

SUMMARY OF THE INVENTION

To minimize the limitations in the prior art, and to minimize otherlimitations that will be apparent upon reading and understanding thepresent specification, the present invention describes a system andmethod for facilitating transactions of scheduled appointment and leadrecords concerning business opportunities in the real estate industry.The service provider may provide a mobile application platform to realestate client users, or realtor-clients, who may access differenttransactional opportunities in the form of leads or pre-scheduledappointments, which have been converted into trackable records such aslead records or scheduled appointment records, with interested buyers orsellers of real property.

A system for transacting scheduled appointments, in accordance with anexemplary embodiment of the present invention, comprises: a serverincluding a network interface for communicating with one or more clientdevices, and one or more processors configured to: receive qualifiedlead information concerning one or more real estate transactionopportunities; generate a scheduled appointment record from thequalified lead information; match a geographic location relevant to auser with the geographic location associated with the scheduledappointment record; provide the scheduled appointment record to a clientdevice associated with the user; and register a transaction with theclient device concerning the scheduled appointment record.

A system for transacting scheduled appointments, in accordance withanother exemplary embodiment of the present invention, comprises: aserver including a network interface for communicating with one or moreclient devices, and one or more processors configured to: generate anoffer for a scheduled appointment record concerning a proposedtransaction; provide the offer for the scheduled appointment record to aclient device; register a transaction with the client device concerningan acceptance of the offer; assign a first predetermined time period tothe scheduled appointment record; monitor, via the client device, aprogress status associated with the proposed transaction; determinewhether the first time period has lapsed prior to a consummation of theproposed transaction; and either: register with the client device theconsummation of the proposed transaction; or assign a secondpredetermined time period to the scheduled appointment record if thefirst predetermined period has lapsed prior to the consummation of theproposed transaction.

A method for transacting scheduled appointments, in accordance withpractice of an exemplary embodiment of the present invention, comprises:receiving qualified lead information concerning one or more real estatetransaction opportunities; generating a scheduled appointment recordfrom the qualified lead information; providing the client device withthe scheduled appointment record; and registering a transaction with theclient device concerning the scheduled appointment record.

A method for transacting scheduled appointments, in accordance withpractice of another exemplary embodiment of the present invention,comprises: generating an offer for a scheduled appointment recordconcerning a proposed transaction; providing the offer for the scheduledappointment record to a client device; registering a transaction withthe client device concerning an acceptance of the offer; assigning afirst predetermined time period to the scheduled appointment record;monitoring, via the client device, a progress status associated with theproposed transaction; determining whether the first time period haslapsed prior to a consummation of the proposed transaction; and either:registering with the client device the consummation of the proposedtransaction; or assigning a second predetermined time period to thescheduled appointment record if the first predetermined period haslapsed prior to the consummation of the proposed transaction.

It is an objective of the present invention to facilitate thetransacting of scheduled events concerning real estate transactions.

It is another objective of the present invention to provide a systemthat connects realtors to individuals or entities interested inconsummating a real estate transaction.

It is yet an another objective of the present invention to provide asystem that generates multiple opportunities from a single leadconcerning a real estate transaction.

It is yet an another objective of the present invention to provide asystem that facilitates data mining or aggregation opportunities in thereal estate industry.

It is yet another objective of the present invention to provide a systemthat may implement an exchange platform for transacting lead records andscheduled appointment records.

These and other objectives, advantages and features of the presentinvention are described herein with specificity so as to make thepresent invention understandable to one of ordinary skill in the art.

BRIEF DESCRIPTION OF DRAWINGS

Elements in the figures have not necessarily been drawn to scale inorder to enhance their clarity and improve understanding of thesevarious elements and embodiments of the present invention. Furthermore,elements that are known to be common and well understood to those in theindustry are not depicted in order to provide a clear view of thevarious embodiments of the invention.

FIG. 1(a) illustrates an entity relationship diagram of a business modelthat may be practiced in accordance with the present invention.

FIG. 1(b) illustrates a system in accordance with one embodiment of thepresent invention.

FIG. 2(a) illustrates a computer-readable medium for transactingscheduled appointment records and lead records via a user interface madeavailable to a plurality of client devices, in accordance with oneembodiment of the present invention.

FIG. 2(b) illustrates exemplary embodiments of data structures for alead record, a scheduled appointment record, and an offer record.

FIG. 3 illustrates a flowchart depicting method 300 for transacting alead record or scheduled appointment record, in accordance with practiceof one embodiment of the present invention.

FIG. 4 illustrates a flowchart depicting a method for generating andmanaging records, in accordance with practice of one embodiment of thepresent invention.

FIG. 5 illustrates a flowchart depicting a method for transactingrecords in accordance with practice of one embodiment of the presentinvention.

FIG. 6 illustrates a flowchart depicting a method for managing anddistributing scheduled appointment records and lead records, inaccordance with practice of one embodiment of the present invention.

FIG. 7 illustrates a flowchart depicting a method for distributinginformation concerning scheduled appointment records and othertransactional opportunities, in accordance with practice of oneembodiment of the present invention.

FIG. 8 illustrates a method for gathering user data associated with thetransacting of scheduled appointment records and lead records, inaccordance with practice of one embodiment the present invention.

FIG. 9 illustrates a method for distributing scheduled appointmentrecords or lead records via a user interface on a client device, inaccordance with practice of one embodiment of the present invention.

FIG. 10 illustrates an exemplary dashboard for a GUI configured fortransacting scheduled appointment records, in accordance with oneembodiment of the present invention.

FIG. 11 illustrates an exemplary location-based interface for providingclient devices with available scheduled appointment records, leadrecords, or other transaction opportunities, in accordance with oneembodiment of the present invention.

FIG. 12 illustrates an exemplary management tool interface for assistingrealtor-clients with transacting scheduled appointment records, inaccordance with one embodiment of the present invention.

FIG. 13 illustrates an exemplary user interface configured to facilitatethe transaction of scheduled appointment records, in accordance with oneembodiment of the present invention.

FIG. 14 illustrates an exemplary interface for providing atime-sensitive offer to purchase a scheduled appointment record.

FIG. 15 illustrates an exemplary management tool for assistingrealtor-clients with managing their purchased leads or purchasedscheduled appointment records, in accordance with one embodiment of thepresent invention.

FIG. 16 illustrates an exemplary interface for facilitating themanagement of purchased scheduled appointment records, in accordancewith one embodiment of the present invention.

FIG. 17 illustrates another exemplary interface for facilitating themanagement of purchased scheduled appointment records, in accordancewith one embodiment of the present invention.

FIG. 18 illustrates another exemplary interface for facilitating themanagement of purchased scheduled appointment records, in accordancewith one embodiment of the present invention.

FIG. 19 illustrates an exemplary interface for requesting user dataassociated with one or more transactions of scheduled appointmentrecords.

FIG. 20 illustrates an exemplary user interface configured to providenotifications concerning available transaction opportunities, inaccordance with one embodiment of the present invention.

FIG. 21 illustrates an exemplary interface for requesting user dataassociated with one or more transactions of scheduled appointmentrecords.

FIG. 22 illustrates another exemplary management tool for assistingrealtor-clients with managing their purchased leads or purchasedscheduled appointment records, in accordance with one embodiment of thepresent invention.

FIG. 23 illustrates an exemplary social media platform provided via theuser interface, in accordance with one embodiment of the presentinvention.

FIG. 24 illustrates an exemplary user interface, which implements anincentive-based algorithm, in accordance with one embodiment of thepresent invention.

DESCRIPTION OF THE INVENTION

In the following discussion that addresses a number of embodiments andapplications of the present invention, reference is made to theaccompanying drawings that form a part thereof, where depictions aremade, by way of illustration, of specific embodiments in which theinvention may be practiced. It is to be understood that otherembodiments may be utilized and changes may be made without departingfrom the scope of the invention. Wherever possible, the same referencenumbers are used in the drawings and the following description to referto the same or similar elements. While embodiments of the disclosure maybe described, modifications, adaptations, and other implementations arepossible. For example, substitutions, additions, or modifications may bemade to the elements illustrated in the drawings, and the methodsdescribed herein may be modified by substituting, reordering, or addingstages to the disclosed methods. Accordingly, the following detaileddescription does not limit the disclosure. Instead, the proper scope ofthe disclosure is defined by the appended claims.

In the present specification, the term seller may include anyindividual, group of individuals, or legal entity that is interested inselling real property. A buyer may refer to any individual, group ofindividuals, or legal entity that is interested in purchasing realproperty. A realtor may refer to any individual, group of individuals,or entity that is licensed to sell, purchase, lease, or otherwisefacilitate others with consummating real estate transactions.Transactional opportunities may refer to leads, qualified leads, orscheduled appointments concerning proposed transactions in real estate.Leads may refer to an opportunity to list real property with arealtor—and may include general or personal information of an interestedbuyer, an interested seller, real property information, or anymarketing, advertising, or other information concerning a real estatetransaction, including a party's interest in buying, selling, leasing,or renting real property. Qualified leads may refer to leads that havebeen automatically or systematically qualified as leads suitable forgenerating a lead record or a scheduled appointment record. Lead recordsmay be records containing lead or qualified lead information. Scheduledappointment records may be records containing lead or qualified leadinformation, which have been confirmed and generated with specificscheduled dates and times for pursuing a real estate transaction. Usersor realtor-clients may refer to realtors, or non-realtor users of thesystem, who may access the system's server via an application to receiveoffers concerning qualified leads or scheduled appointment records.

Generally, the present invention involves a system and method forfacilitating transactions concerning leads and scheduled appointments inthe real estate industry. The system may be configured to receiveinformation concerning transactional opportunities, or leads, pertainingto one or more parties interested in pursuing a real estate transaction.Each lead may be followed-up, verified, or qualified to ensure that realparties interested in consummating a real estate transaction are willingand able to, for example, schedule a particular time and date to meetwith a realtor. Once a lead has been qualified, a record of that leadmay be generated and stored as a qualified lead record. Similarly,qualified leads may be utilized to generate scheduled appointmentrecords, which include an agreed-upon time and date for the interestedparty to meet with a realtor-client of the system. These lead recordsand scheduled appointment records may then be offered to realtor-clientsof the system via a mobile device application that allows an interestedrealtor-client to purchase or bid on one or more records. Furthermore,an exchange platform may be implemented so that affiliates orthird-party participants may offer their own lead records to therealtor-clients of the system.

In exemplary embodiments, a system and method for transacting qualifiedlead records and scheduled appointment records works preferably with amembership-based business model that dictates a realtor-client's accessto the lead records and scheduled appointment records offered by aservice provider. Such business model is facilitated via acomputer-readable medium configured to procure, cultivate, anddistribute offers concerning such transactional opportunities.

For example, an exemplary system may comprise of a computer readablemedium, such as a server, configured to access a database ofrealtor-clients and real estate related leads from buyers, sellers,renters, lessors, or other realtors. These leads may be autonomously orsystematically analyzed to identify viable transactional opportunitiesin order to generate offers based on lead records or scheduleappointment records that include a specific interested party, date, andtime for an appointment concerning a proposed real estate transaction.In some embodiments, each lead or scheduled appointment record may beprovided to a plurality of realtor-clients via a plurality of clientdevices configured with a graphical user interface or GUI that displaysoffer records in one or more geographic locations relevant to eachrealtor-client. In some exemplary embodiments, each record may bemonitored, categorized, and reassigned in a predetermined manner andoffered to one or more alternative realtor-clients. As such, uponreceipt of a request from a realtor-client for a selected record, thesystem may register a transaction concerning the lead or scheduledappointment with the realtor-client's device. As mentioned above,transactions of the leads or scheduled appointments may include offeringthe records for sale, as well as auctioning of the lead records andscheduled appointment records.

In exemplary embodiments, the system may incorporate an algorithm formatching prospective owners—such as buyers or sellers of realestate—with compatible realtor-clients that match one or morepredetermined parameters.

In exemplary embodiments, the system may offer a service provider with aplatform suitable for data mining or data aggregation capabilities tocontinuously extrapolate transactional opportunities such as leads fromrealtor-clients, which may be monitored and offered back to otherrealtor-clients of the system.

In exemplary embodiments, the system may incorporate an incentive-basedalgorithm to help improve each realtor-client's success and maximizeeach transactional opportunity.

In exemplary embodiments, the system may incorporate an exchangeplatform, which enables affiliates or third-party participants tointroduce offers concerning their own lead records to therealtor-clients of the system.

The following figures illustrate several exemplary embodiments of asystem and user interface in accordance with the present invention, aswell as several methods, processes or algorithms that may be implementedby such system.

FIG. 1(a) illustrates an entity relationship diagram of a system andbusiness model that may be practiced in accordance with the presentinvention. More specifically, FIG. 1(a) depicts an entity relationshipdiagram for system 100, wherein the entities, for which data may bestored and managed, include owners 1, real property 2, leads 3, leadtier protocols 4, sources 5, offers 6, realtor-clients 7, roles 8,transaction protocols 9, social media 10, and agent specialty 11.

A system and business model that may be practiced in accordance with thepresent invention, includes a membership-based business model thatprovides users access to different quantities and or types of offersconcerning transactional opportunities in real estate. In exemplaryembodiments, different memberships may offer users of the systemdifferent access privileges to the offers provided. The offers typicallyinvolve owners of real property that are presently or have been in thepast, interested in consummating a real estate transaction. The offersare generated from a lead depository, which is supplied and replenishedfrom one or more sources that may be integral or affiliated with theservice provider. More importantly, the business model implements a setof unique lead management protocols for managing each lead andgenerating different types of offers including pre-arranged scheduledappointments.

Accordingly, owners 1 may be individuals or entities owning realproperty that they wish to sell, or entities that are interested inpurchasing, or even leasing, real property; properties 2 may be one ormore physical locations that are owned by the one or more owners 1 andcan be, or have been in the past, the subject of a lead. Leads 3 mayinclude one or more opportunities to list one or more of the properties2 with a realtor.

Lead tier protocols 4 may include one or more protocols for managingdifferent caliber leads, in order to maximize transacting opportunities.Lead tier 4 protocols may dictate how a lead is categorized and handledat every step of the process—from acquiring the lead, to generating alead record or a scheduled appointment record from that lead, togenerating an offer record that is provided to one or morerealtor-clients of system 100. For example, and as will be described inmore detail below, these protocols may dictate: the duration of an offerrecord concerning a lead record or scheduled appointment record; theprice at which each lead record or scheduled appointment record may beoffered; which realtor-clients will have access to a particular offerrecord; and where within the system the offer record will be listed.

Sources 5 may include individuals or entities that help generate leads3. Sources 5 may include lead generation efforts internal to the serviceprovider, or may include external efforts from listing agencies or otheraffiliates (or even other realtor-clients of system 100) that provideleads to system 100. In exemplary embodiments, sources 5 may implementrevenue share tracking methods for tracking which sources have providedthe most profitable leads.

Offers 6 are offers for the lead records or scheduled appointmentrecords generated from leads 3, which may be offered either directly toone or more realtor-clients, or to all realtor-clients in a region.Offers 6 may include time-sensitive offers and other attributes dictatedby the protocols of lead tier protocols 4, such as timing and pricing.As will be discussed in detail below, a lead may be offered multipletimes, even simultaneously and to multiple realtor-clients.

Realtor-clients 7 are the users of system 100. These users of system 100are typically although not necessarily registered users. In exemplaryembodiments, realtor-clients' access to offer records may be governed byassigned roles such as subscriptions to the services provided by theservice provider. For example, and without limiting the scope of theinvention, the service provider may offer one or more membershipcategories or levels that define different access privileges to varyingtypes of offer records.

Roles 8 may include the roles, access or permissions allotted torealtor-clients 7 of system 100. Accordingly, roles 8 may be defined bya role-based access control model that dictates the types and orquantities of offers accessible to each realtor-client. In someembodiments, such role-based access control model may be implemented byintroducing a membership scheme. For example, and without limiting thescope of the present invention, a realtor-client may choose from one ormore membership types, levels, or categories that will grant thatrealtor-client access to different types of offers for lead records,scheduled appointment records, or other transactional opportunitiesduring a predetermined membership period.

In some embodiments, membership may dictate a predetermined period oftime during which to receive and or accept a certain number of offerrecords. In other embodiments, membership may dictate the types of offerrecords a realtor-client is allowed to access, purchase, or bid on. Inyet other embodiments, membership may dictate how a realtor-client isprovided access to these offers—for example, a realtor-client withaccess privileges under a first membership class may receivenotifications directly and exclusively to their mobile device, whilerealtor-clients with access privileges under a second membership classmay only access offers provided via a list of available lead recordsoffered to multiple realtor-clients at the same time. Naturally,different variations may be implemented without deviating from the scopeof the present invention. Accordingly, a membership scheme may be onebasis for determining one of the roles 8 assigned to each ofrealtor-clients 7 of system 100.

Transaction protocols 9 may include any transaction method or medium bywhich realtor-clients 7 may purchase, bid, or otherwise transact in theoffer records for leads, scheduled appointments, or transactionalopportunities that system 100 offers.

Social media 10 may include the addresses, links, subscriptions, orsocial media services to which realtor-clients 7 may subscribe to andutilize. This information may be useful for enabling various functionsand tools for realtor-clients to manage posts, newsfeeds, and othersocial media tools within system 100.

Agent Specialties 11 may include the various specialties ofrealtor-clients 7, such as: buyer's agent, listing agent, foreclosures,short-sales, property management, townhouses, condos, haunted houses, orany other number of specialties that may describe the particular focusof a realtor-client. This information may be useful for targeting offersto those realtor-clients that will be better suited for a particularsituation. For example, in some embodiments, offers comprising leadrecords or scheduled appointment records concerning a foreclosure may beprovided to a realtor-client that specializes in foreclosures.

Implementing system 100 will enable the management of leads received,generate quality offer records—concerning lead records or scheduledappointment records based on those leads—and enable management of therecords by implementing a set of one or more protocols for determininghow long an offer is listed, what price an offer may be offered for andto whom, and where within the system the offer will be listed.

Turning to the next figure, FIG. 1(b) illustrates the components ofsystem 100 in accordance with one exemplary embodiment. Generally,system 100 comprises of service provider 101, affiliates 102, and clientdevices 103 and 104, which communicate with one or more servers(106-108) via network 105, such as the Internet. A database 109 orseveral databases may be accessible to the one or more servers andimplemented in order to store user information, lead information, leadrecords and scheduled appointment records, service areas or geographicregion information, owner information, real property information, andother information that may be relevant to service provider 101.

Service provider 101 may obtain leads or lead information from sourcessuch as affiliates 102, which may include without limitation, thirdparty affiliates or any other suitable resources for obtaining leads,including any internal or external data mining resources that may beavailable to service provider 101. For example, affiliates 102 maycomprise one or more parties that make up sources 5. Typically, serviceprovider 101 may distribute a user interface such as a graphical userinterface (GUI) to client devices 103 and 104 via a downloadable mobileapplication or even a web GUI such as a website.

One or more servers may manage several aspects of system 100. Forexample, and without deviating from the scope of the present invention,a GUI server 106 may be dedicated to services such as web GUI servicesor mobile application services. A geographic location services server orGLS server 107 may be implemented for providing geographic locationservices. For example, GLS server 107 may facilitate identifying leadrecords or scheduled appointment records associated with real propertylocated within a geographic region relevant to a realtor-client. Aprocess server or main server 108 may be implemented to handle thevarious requests for information, as well as overseeing transactions ofthe scheduled appointment records that are purchased, auctioned, orotherwise transacted in system 100. Naturally, system 100 may beconfigured to perform its tasks with multiple servers or a single serverwithout deviating from the scope of the present invention.

FIG. 2(a) illustrates a computer-readable medium for transacting leadrecords or scheduled appointment records via a user interface madeavailable to a plurality of client devices, in accordance with oneembodiment of the present invention. More specifically, FIG. 2(a)illustrates a block diagram of server 201, which includes storage module202, communications module 203, control module 204 and software module205. Moreover, server 201 includes GUI client 206, GLS client 207,realtor client 208, owner client 209, and affiliate client 210.

In an exemplary embodiment, server 201 may comprise a two tier serversetup with one database layer and one application (web server) layer.This may allow the system to scale user wise by load balancing theapplication layer and also provide increased security. A cloud basedsystem may run on servers in the Amazon Virtual Private Cloudenvironment. All physical documents as well as database backups may beencrypted and stored in Amazon's Simple Storage Service (S3). Fordisaster recovery purposes the system may implement a backup of allcurrent layer images stored in S3 and backups of the database performedincrementally every X minutes and full daily backups. For highavailability (and also disaster recovery) purposes based on the serviceprovider's requirements, the system may address failover clustering thedatabase server as well. All security and firewalls may be configuredusing best practices and industry standard methods. Access to serversmay be limited and monitored. All system access attempts (success orfailure) may be logged in the database and physical log files as well asaccess to any base entities.

In other embodiments, server 201 may be a distributed server system setup for robustness in case one server fails. In such exemplaryembodiment, server 201 is a World Wide Web (WWW) server connected to theinternet. Server 201 may comprise representational state transfer (REST)architecture. Although other architectures may be implemented, a RESTserver may be desirable to maximize efficiency, particularly in systemsthat may experience an increasing amount of requests. Furthermore,similar architectures may provide a centralized means of connecting withother system components such as third-party applications or websitesthat may provide services including websites or mobile deviceapplications and geographic location services. Server 201 may compriseof a plurality of distributed servers configured for fault tolerance,duplication and backup capabilities.

Naturally, server 201 may be configured with any known techniques and inany known manner to achieve a desired security and functionality.Whatever architecture, technique or manner in which server 201 isimplemented, server 201 is typically configured to: receive qualifiedlead information concerning one or more real estate transactionopportunities; generate a lead record and or a scheduled appointmentrecord from the qualified lead information; generate an offer includingthe lead record and or scheduled appointment record; provide the offerto a client device; and register a transaction concerning the offer withthe client device.

In some embodiments, a GLS client may facilitate server 201 withimplementing geographic location services. For example, and withoutlimiting the scope of the present invention, server 201 may be furtherconfigured to match a geographic location relevant to a realtor-clientwith the geographic location associated with the scheduled appointmentrecord, in order to provide that realtor-client only with offer recordssituated in a particular geographic region, which the realtor-client mayhave previously selected. In alternative embodiments, server 201 may befurther configured to match a geographic location of a client devicewith the geographic location associated with the offer record in orderto display on a client device only the scheduled appointments in thevicinity of that device. As may be appreciated, different variations oflocation-based services may be incorporated without deviating from thescope of the present invention.

Storage module 202 may be coupled either externally or internally toserver 201. For example, storage 202 may be one or more long term memorystorage devices, such as a hard drive, disk drive, tape unit, NetworkAttached Storage (NAS) device, Storage Attached Network (SAN) device,RAID disk array, or optical disk array. Although typically a long termmemory storage device, storage 202 may be any other memory devicewithout departing from the scope of the present invention. In anexemplary embodiment, storage 202 is striped across redundant storagecontainers or RAID disk array in a SAN environment for increased dataaccess speeds and robustness. Of course, any other storage configurationwould not deviate from the scope of the present invention so long asstorage 202 is suitable for the needs of server 202. In one exemplaryembodiment, storage module 202 is a cloud-based storage solutionsuitable to host one or more databases for the system managed by server201.

Storage module 202 may hold multiple databases containing data objectswithin data repositories collected by server 201. The databases ofstorage module 202 may be created by a known database manager usingknown technologies such as relational architecture and SQL access, suchas Microsoft™ SQL or Oracle™ DB. However, the database of storage module202 may be as simple as a series of files stored in a directory, with atext file listing filename locations without departing from the scope ofthe present invention. In one embodiment, the one or more databases ofstorage module 202 may be a combination of a known database manager, andan organized directory tree structure, wherein the database managerstores text information in the database itself, but stores multimediainformation and other non-text information as filename locations offiles stored in an organized directory tree structure.

In an embodiment wherein server 201 relies on cloud computing, storagemodule 202 may include technologies offered by Amazon™ such as Amazon™Elastic Compute Cloud (AWS EC2), whereby storage module 202 may employMySQL™ and AWS EC2™ instances.

The one or more databases of storage module 202 may hold multiple datarepositories corresponding to: owners such as prospective buyers orsellers of real property; real property information; sources oraffiliates such as entities that supply the system with leads; leadrecords and scheduled appointment records that have been generated fromleads; realtor-clients; the various roles or access privileges that maygovern each realtor-client's access to offer records; service areas;offer records; lead tier protocols or rules that govern differentaspects of each record; and any other useful information that may beobtained via suitable data mining resources and utilized to continuouslygenerate new leads.

Communications module 203 may be implemented as a single device ormultiple devices configured to connect server 201 to a network such asthe internet, and or communicate server 201 to other system components,including other servers such as web servers, mobile device applicationservers, and/or a geographic location services servers.

Control module 204 typically includes one or more processors and memoryconfigured to execute a set of one or more executable instructions suchas program code and/or data stored on one or more computer readablemediums to implement the various applications, data, steps describedbelow and any other instructions pertinent to the functions of server201. For example, such executable instructions may be included insoftware module 205.

Software module 205 may include one or more modules for the variousfunctions of the system managed by server 201. For example, and withoutlimiting the scope of the present invention, software module 205 mayinclude a lead management module to implement lead tier protocols, arecord dispatch module for matching offers to best-suitedrealtor-clients, a data aggregation module for requesting and gatheringinformation from realtor-clients, a membership ranking module forimplementing an incentive-based program for realtor-clients, a paymentsmodule for handling payments for the offer records concerning leadrecords and scheduled appointment records, and other software modulesthat help create, track and monitor opportunities for realtor-clients ofthe system.

Moreover, software module 205 is typically configured to facilitatecustomer relationship management (CRM) functions and reporting. Forexample, and without deviating from the scope of the present invention,once a realtor-client selects and purchases an offer record, the leadrecord or scheduled appointment record associated with the offer recordmay be stored in a history or prospects tab ultimately to make its wayto a reporting tool that allows for the realtor-client to manage his orher leads.

Moreover, software module 205 is typically configured to facilitatesending requests for information between realtors. For example, andwithout deviating from the scope of the present invention, realtors maybe able to post a questions and receive answers on a live platform.

Server 201 may include various clients, such GUI client 206, GLS client207, realtor client 208, owner client 209, and affiliate client 210.These clients may include hardware components and software componentsconfigured to communicate with server 201 in order to receive requestsfrom client devices, use location-based methods to provide relevantrecords, handle the various requests for information, as well asoverseeing transactions of the leads or scheduled appointment recordsthat are purchased, auctioned, or otherwise transacted in the system viaserver 201.

Turning now to FIG. 2(b), several exemplary embodiments of datastructures utilized by a system in accordance with the present inventionare illustrated. More specifically, FIG. 2(b) exemplarily illustratesembodiments of data structures for a lead record, a scheduledappointment record, and an offer record—such as lead record 211,scheduled appointment record 212, offer record 213, and offer record214.

A lead record in accordance with the present invention typicallyincludes pertinent information concerning a lead that has been receivedby system 100 via affiliates 102 or a similar lead exchange platform.Lead record 211 may include a lead ID 221 for identifying and keepingtrack of lead record 211; a property ID 222 for identifying orreferencing real property that is the subject of a lead; an owner ID 223for identifying an owner (for example a seller that is interested inselling a property associated with the property ID); source ID 224 foridentifying a source of the lead information; a CRM ID 225 for aggregatereporting purposes; lead type 226 indicator for identifying the type oflead—such as a lead for a potential sale or a lead for a potential buy;lead tier 227 for indicating a lead category according to a protocol formanaging lead records and scheduled appointment records; lead price 228for designating a predetermined price for the record; dispatchinformation 229 concerning comments or useful information that may helpsell the lead; and lead status 230 may provide an indicator for keepingtrack of whether lead record 211 is active, has been sold, or is nolonger available for generating an offer record.

Lead record 211 refers to and may be generated from various informationand other records stored in the one or more databases of system 100. Forexample, and without limiting the scope of the present invention,property ID 222 may refer to a property record (stored in one or moredatabases of system 100) of a particular property including the propertyaddress, the property type, a square-footage, number of bedrooms, numberof bathrooms, and lot size. Owner ID 223 may refer to an owner record(stored in one or more databases of system 100) of an individual orentity including the owner's name and last name, or entity name,address, phone number, and email address. Source ID 224 may refer to asource record (stored in one or more databases of system 100) of a leadsource including the source's individual or entity name, lead cost (i.e.cost at which the lead information may have been purchased from the leadsource, or even a lead rate indicative of a percentage commission thatmay be supplied to the lead source in the event the lead record isoffered and sold). Lead type 226 may designate a lead type indicative ofthe type of transaction sought by an interested party (e.g. owner ID223) such as a lead for a potential purchase or a lead for a potentialsale of the property identified by property ID 222. Lead tier 227 mayrefer to a lead category as may be defined by lead tier protocols andmay dictate the timing, pricing, and means in which an offer recordbased on lead record 211 may be offered to one or more realtor-clients.Lead price 228 may be a suggested or predetermined price for lead record211 and as will be discussed below may be adjusted or updated inaccordance with lead tier 227 or the category assigned to lead record211 prior to being offered. Dispatch information 229 may be generated atthe time lead record 211 is created or may be extracted from the lead orqualified lead concerning the owner or property associated with leadrecord 211. For example, dispatch information 229 may comprise pertinentinformation such as an urgency to sell due to a divorce, personalinformation such as a preferred language spoken by the owner, or anyother pertinent information that may be useful to a realtor-client; thisinformation may be included in an offer record associated with leadrecord 211.

Scheduled appointment record 212 is similar to lead record 211.Moreover, scheduled appointment records may be a type of lead recordoffered by the system whereby an actual date, time and place for a livemeeting has been confirmed by an interested party. As such, an exemplaryscheduled appointment record 212 may include the same information aslead record 211 with the additional scheduled information 231. This mayoccur when a lead record is followed-up on by a service provideradministrator or agent for the service provider. For example, an agentof the service provider may contact an owner identified by lead record211 and confirmed that a specific date, time and place for a meetingwith a realtor is desired. Accordingly, in addition to the informationthat is included with lead record 211, scheduled appointment record 212may include said scheduled information 231. Similarly, scheduledappointment record 212 may include a different lead price, such as leadprice 228 a because the value of the record is typically elevated due tothe fact that the opportunity of a specific date, time and place meetingcreates a better prospect than when the realtor-client purchases a leadrecord that will require the realtor-client to advance the prospectivetransaction on their own. A pre-scheduled meeting carries particularvalue to a realtor, and as such, scheduled appointment records may bevalued different. Of course, other factors may alter a lead value, suchas the lead tier and any dispatch information that may increase ordecrease the chances of a successful prospective transaction.

Offer records such as offer record 213 may be generated from lead record211 or scheduled appointment record 212. In the exemplary embodimentshown, offer record 213 is an offer concerning scheduled appointmentrecord 212. Accordingly, offer record 213 may include offer record ID232, lead ID 221 (to keep track of the lead from which offer record 213was based), offer type 233, offer timer 234, offer cap 235, agent ID236, lead tier 227, lead price 228 a and scheduled information 231.

Offer type 233 may designate a method in which offer record 213 isprovided to one or more realtor-clients. In an exemplary embodiment,offer type 233 may be designated as ‘individual’ or ‘market’ whichindicates whether the offer will be delivered via system 100 to a singlerealtor-client or a plurality of realtor-clients. For example, offerrecord 213 may be an offer concerning scheduled appointment record 212,and may have an offer type 233 designating offer record 213 for‘individual’ delivery. Accordingly, in this example, offer record 213may be provided to a single realtor-client, which may have beenpreviously identified based on known parameters including: thatrealtor-client's role or permissions based on a membership subscription;a geographic region or location of the property associated with propertyID 222, a specialty of the realtor-client listed in the realtor-client'sprofile, and any other information or parameters that points towardsoffer record 213 being a good fit for the targeted realtor-client (i.e.and having a high likelihood that the targeted realtor-client willaccept the offer and succeed in consummating the transaction proposed bythe interested party). Of course, without limiting the scope of thepresent invention, other offer types may include several variations onthe above, such as an offer type that allows offer record 213 to bedelivered to more than one realtor-client simultaneously but notnecessarily every realtor-client in the system or ‘market’ at the sametime.

Offer timer 234 may refer to a predetermined time period during which arealtor-client, to whom offer record 213 has been provided, can acceptor decline the offer. The predetermined time period may be based on leadtier 227. A timer for an offer such as offer 213 (concerning scheduledappointment record 212) may be desirable because of the time-sensitivenature of a scheduled appointment. Moreover, a timer may provide anincentive to realtor-clients that know this opportunity may be passed onto another realtor-client if the targeted realtor-client declines.

Offer cap 235 may refer to a designation of how many times offer record213 is offered before there is a cool-down period. For example, offercap 234 may be set at 5 times. As such, if a first realtor-client isdelivered offer record 213 and that first realtor-client does not acceptor declines the offer, offer record 213 may be provided to a secondmatching realtor-client. If, however, offer record 235 has been offered(i.e. delivered) to a fifth realtor-client and declined, offer cap 234will prevent the system from delivering offer record 235 to a sixthrealtor-client. This will allow the system administrators time tore-review and reassess the lead or qualified lead information, as wellas review any feedback from the realtor-clients declining the offerrecord; for example, there may be some factors that realtors are awareof concerning the property associated with property ID 223, or any othernumber of factors that the service provider is unaware of but may learnfrom such feedback. Moreover, during a predetermined cooldown period,agents for the service provider may decide to amend lead price 228 a,re-categorize or re-assign lead tier 227, or generate a new offer recordaltogether.

Agent ID 236 may refer to a realtor record (stored in one or moredatabases of system 100) of an individual or entity associated with arealtor-client including the realtor's name and last name, or entityname, realtor's license number, address, phone number, email address,specialty or professional profile, contact preferences, and role (i.e.membership and subscription status). Typically, agent ID 236 is anidentification associated with the realtor-client to whom offer 213 isdelivered. In some circumstances, agent ID 236 may include more than oneID if offer record 213 is delivered to a plurality of realtor-clients.In other embodiments, agent ID may not be part of an offer record, forexample if the offer record is designated ‘market’ and targeted to allrealtor-clients in a particular region. In yet other embodiments, theoffer record may include a role identifier such as role ID 243 thatindicates which realtor-clients of system 100 are eligible to receive orhave access to a particular offer record.

Offer information 237 may be information generated or extrapolated fromdispatch information 229. Typically, this offer information 237 mayprovide key facts or desirable attributes about lead record 211 or (inthis case) scheduled appointment record 212, which may be attractive tothe realtor-client associated with agent ID 236. Other than beinginformative, offer information 237 may also serve as a marketing meansto garner interest in offer record 213 and heighten the likelihood thatoffer record 213 will be accepted (whether by purchase or bid) by therealtor-client associated with agent ID 236 or with access to offerrecord 213 per role ID 243.

Offer record 214 is a similar offer record to offer record 213, but onebased on a lead record, thus not including scheduling information suchas scheduled information 231. Further, offer record 214 does not includeagent ID 236 but role ID 243 associated with a role designation that maydictate to which realtor-clients offer record 214 may be delivered, orwhich realtor-clients of system 100 may even have access to offer record214. Because offer record 214 is exemplarily generated from a differentlead record than lead record 211, offer record 214 will have a differentlead ID 239, and may have a different offer type 240, offer timer 241,offer cap 242, lead tier 244, and lead price 245—depending on the typeand quality of the lead information that is associated with the leadrecord being offered through offer 214. Similarly, offer information 246will be typically tailored to the particular facts of the leadinformation on which offer 214 is based, or in some embodiments, offerinformation 246 may also comprise a predetermined message based on roleID 243, offer type 240, lead tier 244, lead price 245, or anycombination thereof.

Of course, other variations of lead records, scheduled appointmentrecords, and offer records may be possible and organized and structuredwith more or less data without deviating from the scope of the presentinvention.

Turning to the next several figures, methods in accordance with thepresent invention are discussed in turn.

FIG. 3 illustrates a flowchart depicting method 300 for transacting alead record or scheduled appointment record, in accordance with practiceof one embodiment of the present invention. Although method 300 is shownin a particular sequence of steps, other conceivable sequence of thesteps may be practiced without deviating from the scope of the presentinvention. In an exemplary embodiment, method 300 comprises: receivingqualified lead information concerning one or more real estatetransaction opportunities (301); generating a record, such as a leadrecord or a scheduled appointment record from the qualified leadinformation (302); determining one or more target realtor-clients basedon a set of one or more parameters (303); providing the lead orscheduled appointment record to a client device associated with the oneor more targeted realtor-clients (304); and registering a transactionwith the client device concerning the scheduled appointment record(305).

In step 301 a lead received from a source such as affiliates 102 may bechecked for accuracy, quality, and thus qualified as a qualified lead.Information pertinent to the lead or qualified lead may be confirmed andentered into a database of the system to create a qualified lead record.This record may include information pertaining to the identity of anowner of real property or an entity interested in a particular property,the geographic location or address of the real property, and the natureof the entity's interest in the real property with respect to the kindof transactional opportunity sought—i.e. purchase, sale, or lease. Assuch, in exemplary embodiments, qualified lead information concerningone or more real estate transaction opportunities may be received andstored. For example, step 301 may encompass receiving the information byan agent of the service provider and inputting the information in one ormore databases of system 100. Information pertaining to an interestedparty such as an owner of a property may be received and stored in adepository of owners and assigned an owner ID. Similarly, propertyinformation pertaining to the subject matter property of the lead may bestored in a property depository of system 100 and assigned a propertyID. Other information provided with the lead may be aggregated into theone or more databases of system 100, including information that will beattractive to potential realtor-clients to which an offer record may bedelivered.

In step 302 a record may be generated from the lead information in theone or more databases of system 100. For example, and without limitingthe scope of the present invention, once qualified lead information hasbeen confirmed and entered into the system, an agent of the serviceprovider may contact the interested party (e.g. owner of real estateseeking to sell) in order to confirm a specific date, time and place foran appointment with a realtor for pursuing a real estate transaction.

Additionally, in exemplary embodiments, the qualified lead informationmay be tagged, flagged, or otherwise marked with additional informationthat will be helpful to a realtor. Such information may include profileinformation pertaining to the owner/interested party such as sex, race,religion, marriage status, family size, etc. For example, a scheduledappointment record may include information pointing out that an ownerthat has recently divorced is seeking to sell their current home. Otherexamples of additional information may include, without limitation, anindication pertinent to a level of interest or urgency. This informationmay be useful not only for the realtor that ultimately accepts andpurchases or successfully bids on the offer associated with thequalified lead, but also to the service provider—for this informationmay aid valuation of the qualified lead information, and ultimately thescheduled appointment record generated therefrom.

Similarly, a lead record—rather than a scheduled appointment record maybe generated from the lead information. In an exemplary embodiment, alead record may be autonomously generated by one or more softwaremodules that sift through the various depositories and gather relatedinformation to generate a lead record such as lead record 211. In someembodiments, an agent of the service provider may manually enterscheduling information to a lead record in order to generate a scheduledappointment record such as scheduled appointment record 212. In otherembodiments, an interested party or owner may have already provided apreferred time and date for a scheduled appointment and the system mayautomatically generate a scheduled appointment record such as scheduledappointment record 212.

Accordingly, in step 302, a lead record or a scheduled appointmentrecord that includes the qualified lead information may be generated,stored, and prepared for offer via the user interface or GUI provided tousers of system 100. Moreover, in exemplary embodiments, an offer recordsuch as offer records 213 and 214 may be generated from lead records andscheduled appointment records in order to deliver offers concerningleads or scheduled appointments to the realtor-clients of system 100.Offer records are desirable because they contain limited informationthat allow the service provider to track, monitor, and monetize theinformation without having to provide the information included in eachlead record or scheduled appointment record such as the name of theowner, or property information associated with the lead information.

In step 303, a determination may be made concerning one or more targetrealtor-clients to whom to offer the offer record. This determinationmay be based on a wide range of parameters including but not limited to:geographic region of the real property; geographic region of one or moreusers; role or membership status of one or more realtor-clients; role ormembership class of one or more realtor-clients; profile information ofthe interested party or owner associated with the offer record; profileinformation associated with one or more realtor-clients; and any otherparameters that can be useful in determining the best set of one or morerealtor-clients suitable for the offered record.

For example, and without deviating from the scope of the presentinvention, in distributing a scheduled appointment record, system 100may select various parameters in order to reach the most eligiblerealtor-clients that may be interested in the scheduled appointmentrecord, and or will be most likely successful in consummating theanticipated transaction associated with the record. One such parametermay include a geographic region in which the real property or scheduledmeeting associated with the record is located. As such, scheduledappointment records may be offered for purchase or bidding to one ormore users that have indicated an interest in the particulargeographical region.

Similarly, another parameter may include a predetermined role ormembership status or membership class of realtor-clients—this mayinclude determining which realtor-clients may be eligible to receive anoffer concerning the scheduled appointment record. For example, practiceof some embodiments of the present invention may include implementationof membership schemes that allow certain members priority or evenexclusive access to certain types of lead records or scheduledappointment records. As such, a realtor-client's membership may be aparameter that the system utilizes in determining whether to extend(i.e. deliver) the offer record to a client device of one or morerealtor-clients.

Similarly, another parameter or sets of parameters may include profileinformation pertaining to the interested party (e.g. owner of realestate interested in selling) and profile information of one or morerealtor-clients of system 100. This information may be used to matchcompatible personalities, similar backgrounds or spoken language, oreven match an interested party with a realtor-client that specializes inparticular situations (e.g. foreclosures). As profile information cantell the service provider useful information about the parties involved,this information may be used to determine a match that is most likely tosucceed in consummating a transactional opportunity. Additionally, aswill be discussed further below, the service provider may use feedbackfrom a realtor-clients' experience to better aid matching thatrealtor-client with future opportunities.

Accordingly, in step 303, a determination may be made concerning one ormore target realtor-clients for offering the record—this determinationbased on one or more parameters.

In step 304, the offer record may be provided via a GUI or mobile app toone or more targeted realtor-clients. In exemplary embodiments, an offerrecord concerning a lead record or a scheduled appointment record may beprovided via an alert or notification delivered to a client device. Suchalert or notification may launch a mobile application to deliver anoffer for the scheduled appointment record—including an option for therealtor-client to sell or bid on the offer record. Moreover, inexemplary embodiments (see FIG. 5, FIG. 9, FIG. 14 below) apredetermined time limit may be provided with each offer, during which arealtor-client must select to either purchase or make a bid for the leador scheduled appointment.

In step 305, where the offer record is accepted by a realtor-client ofsystem 100, payment is received via a suitable transaction means (i.e.typically via the GUI vehicle in which the offer record is provided) andregistered by the system. Acceptance may include a successful bidamongst several users or a purchase of the offer record. As mentionedabove, depending on the business model implemented, a realtor-clientthat accepts a scheduled appointment record may either: purchase eachrecord at the time of the acceptance of the offer, or may have—per aprior membership agreement—pre-purchased a predetermined number ofrecords for a predetermined period of time. In the former case, wellknown technologies may be implemented to receive payment information viaa suitable transaction module and the payment may be registered bysystem 100; alternatively, each realtor-client may have paymentinformation associated with their account and proper charges may bededucted accordingly. In the latter case, the system may register thepurchase and deduct from any total allotted records per therealtor-client's membership agreement. In any event, if an offer recordis accepted, the transaction may be registered with the client device.

In the event that an offer record is not accepted by any realtor-clientoriginally targeted, a step 303 determination may be re-initiated inorder to determine a new set of one or more realtor-clients that may besuitable for the specific offer.

Turning now to the next figure, FIG. 4. illustrates a flowchartdepicting a method for generating and managing records, in accordancewith practice of one embodiment of the present invention. Althoughmethod 400 is shown in a particular sequence of steps, other conceivablesequence of the steps may be practiced without deviating from the scopeof the present invention.

In an exemplary embodiment, method 400 for generating and managing offerrecords comprises: receiving or accessing lead information (401);qualifying the lead information (402); generating an offer record basedon the qualified lead information (403); displaying the offer record ona user interface accessible to the client devices (404); dispatching orassigning an offer record to a realtor-client (405); determining whetheran agreement concerning the proposed transaction has been secured (406);and either: rehashing the offer record if an agreement was not secured(407), or registering with the client device the consummation of theproposed transaction (408).

To explain the steps above, the first steps 401-403 are similar to thosedisclosed with reference to method 300; the latter steps 404-408 focuson managing an offer record associated with a lead record or scheduledappointment record, wherein management of the offer record depends onwhether the proposed transaction was consummated by the interestedparties with the aid of the realtor to whom the offer record wasdispatched.

In step 401, receiving or accessing lead information may includeidentifying and recording a transaction opportunity from a source suchas affiliates 102. As mentioned above, lead information may be receivedfrom a variety of channels without deviating from the scope of thepresent invention. For example, lead information may be obtained fromdata mining or data aggregation methods, including data aggregationalgorithms implemented with the present system, affiliated websites, orpurchased lists, or a variety of third-party sources.

In step 402, lead information is qualified, which typically involvesconfirming that a lead meets all or some of the criteria to be offeredto a realtor. Qualification can be automated or via a marketing agentphone call, email, or other live means of corresponding with theinterested party.

In step 403, once the service provider connects with the lead andschedules an actual meeting with a time and date, a scheduledappointment record may be generated and entered into the system; anoffer record based on the scheduled appointment record may beautomatically generated or manually created as discussed above.Alternatively, if a specific scheduled time cannot be obtained, or thelead information does not give rise to a scheduled appointment, a leadrecord may be generated instead. Whether a lead record or a scheduledappointment record is generated, an offer record may be generatedtherefrom.

In step 404, the offer record is provided or displayed to one or morerealtor-clients via the GUI. In exemplary embodiments (e.g. see FIG. 9,FIG. 10), notifications via a mobile application may be provided tonotify a realtor-client of an offer record concerning a lead record orscheduled appointment record is available to that realtor-client. Inother exemplary embodiments, an email communication may be sent to arealtor-client. In other embodiments, the offer record is offered alongwith other offer records to a plurality of realtor-clients with roleid's or permissions to access the offer record (see e.g. FIG. 11).

In step 405, the offer record is dispatched to a realtor-client that haseither purchased, successfully bid on, or otherwise accepted the offerrecord to obtain the associated lead record or scheduled appointmentrecord. In exemplary embodiments, this may trigger one or more protocolsfor: tracking that realtor-client's progress with the lead or scheduledappointment; categorizing the lead record or scheduled appointmentrecord in accordance with a predetermined scheme (e.g. see FIG. 6, FIG.7); triggering predetermined time periods allotted for therealtor-client to generate a successful transaction; or triggering othercalls for action that may aid the realtor-client to a successfulconsummation of the proposed transaction (e.g. see FIG. 18).

In step 406, determining whether an agreement concerning the proposedtransaction has been secured, may include determining that therealtor-client is able to secure a listing agreement involving theinterested party or property owner. This may include obtaining feedbackfrom the realtor-client and or confirmation of the transaction by way ofinput from the realtor-client via the client device.

If a lead follow-up or appointment is unsuccessful, in step 407, arehash protocol may be initiated whereby the offer record is sent backto a recycling process that allows the service provider to maximize theability to drive sales by, for example, offering the opportunity to adifferent set of one or more realtor-clients.

If the lead follow-up or appointment was successful, in step 408, thesystem may register with the client device that the consummation of theproposed transaction was successful. This step may be desirable becausethe service provider may have an interest in a predetermined percentageor commission associated with a closing of the proposed transaction.

Turning now to the next figure, FIG. 5 illustrates a flowchart depictinga method for transacting scheduled appointment records in accordancewith practice of one embodiment of the present invention. Morespecifically, method 500 is an exemplary method for providing an offerconcerning a scheduled appointment record, which is time-sensitive andthus expires after a predetermined period of time. It is noted thatalthough method 500 is shown in a particular sequence of steps, otherconceivable sequence of the steps may be practiced without deviatingfrom the scope of the present invention.

In step 501, a scheduled appointment record may be generated—meaningthat a specific date, time, and place for a meeting with an interestedparty has been scheduled; thus because the interested party expects ameeting to occur, the scheduled appointment must be offered on a limitedtime basis, which requires a predetermined time period for the offer toexpire. Accordingly, in one exemplary embodiment, an offer recordconcerning a scheduled appointment record may include time limitationinformation (e.g. offer timer 234) for deriving a duration of an offerrecord and triggering a time limit or count-down for the realtor-clientto accept or decline the offer record.

In step 502, the offer record may be provided to realtor-clients or asingle realtor-client—by for example sending a notification of therecord to at least one targeted realtor-client that has been matchedwith the interested party. In exemplary embodiments, an offer recorddoes not include all the information included in the scheduledappointment record or lead record on which the offer record may be basedon. For example, even though a lead record may include propertyinformation and information concerning the identify of an interestedparty (see FIG. 2(b) for example), an offer record may omit thisinformation so as to conceal it from realtor-clients prior to theiracceptance of the offer record by purchasing or successfully bidding onthe offer record.

In step 503, the system may use the time limitation informationpreviously associated with an offer record in order to generate anactive time limit on the offer. In exemplary embodiments, this mayinclude providing or displaying on the client device an offer recordthat includes a timer. In such embodiments (e.g. see FIG. 14) anotification may be sent to a realtor-client via client device, whichincludes a count-down clock. In other exemplary embodiments, anotification alerts a realtor-client to launch a mobile deviceapplication in which the offer record including a time limitation ortimer is displayed.

As mentioned above, only minimum information is provided in an offerrecord. For example, and without limiting the scope of the presentinvention, an offer record concerning a scheduled appointment record mayinclude a general description of the real property, some minor factsthat may be useful to a potential realtor (i.e. price range, vicinity,etc.) but not include specific information such as contact informationfor the interested party, the interested party's name, or the address ofthe real property at play, or other more pertinent information that maybe available through the lead record or scheduled appointment record.FIG. 13 and FIG. 14 illustrate two possible user interfaces that allowrealtor-clients to view an offer record concerning a scheduledappointment record in order to purchase or bid on.

In steps 504 and 505 determinations may be made depending on whether theallotted time period has expired and or the offer has been accepted.

In step 506, if at least one realtor-client has accepted an offer recordconcerning the scheduled appointment record, the scheduled appointmentrecord is provided to the realtor-client—meaning that all pertinentinformation is made accessible to the realtor-client, including contactinformation or a contact means to contact the interested party or owner,the specific property ID and address associated with the scheduledappointment record, the scheduled date, time and place for the scheduledappointment, and any additional specifics pertaining to the scheduledappointment record.

In step 507, upon confirmation that an offer has been accepted and ascheduled appointment record was provided to a realtor-client, theinterested party or owner of the real property associated with thescheduled appointment record may be notified. In exemplary embodiments,notification to the interested party may include providing detailspertaining to the realtor associated with the realtor-client such asname, and other profile information.

Alternatively, if an offer is not accepted after a predetermined periodof time has expired, the interested party or owner may be notified atstep 508. This may be automated or via correspondence with an agent ofthe service provider. In practice of an embodiment of the invention,this step may include attempting to re-schedule another appointmentdate, time, and place.

Accordingly, at step 509, a determination may be made on whether a newrecord may be generated. For example, where a scheduled appointmentrecord is involved, a determination may be made on whether theinterested party was willing to re-schedule and thus a new scheduledappointment record was generated, or whether the interested party wasunwilling or unable to commit to a new scheduled time for a meeting witha realtor. If a rescheduling was possible, method 500 may bere-initiated from step 501. Alternatively, if rescheduling was notpossible, the information may be used to generate a lead—this may beuseful way to recycle the information for a later time and date. If thisis the case, a new or updated lead record may be generated; this leadrecord may be the subject of a new or updated offer record.

Turning now to FIG. 6, a flowchart depicts a method for managing anddistributing scheduled appointment records, in accordance with practiceof one embodiment of the present invention. More specifically, method600 involves one or more protocols of managing lead records andscheduled appointment records in order to maximize transactingopportunities. A set of protocols such as the steps described by method600 may dictate how a lead is categorized and handled at every step—forexample, how long a lead is listed, what price a lead may be offered forand to whom, and where within the system the lead will be listed. It isnoted that although method 600 is shown in a particular sequence ofsteps, other conceivable sequence of the steps may be practiced withoutdeviating from the scope of the present invention. Method 600 includes aset of rules, protocol or algorithm that maximizes the use oftransactional opportunities such as scheduled appointments or leads.Such method may allow a service provider to re-sell records (ortransactional opportunities) in the event that a first or evensubsequent realtor-clients are unsuccessful. Moreover, different recordcategories may dictate different values or prices at which an offerrecord may be sold or auctioned.

In step 601 an offer record that has been dispatched or accepted by oneor more realtor-clients may be registered or confirmed as dispatched.Accordingly, in exemplary embodiments, the acceptance or delivery of anoffer record to a client device may trigger a set of protocols dictatedby a lead tier or record category that has been assigned to each leadrecord, scheduled appointment records, and thus each offer record.

In step 602, a first record category (e.g. Tier I) associated with theoffer record may be assigned or received. This may include, withoutlimitation, determining or triggering a particular time periodassociated with said first record category.

In step 603, a determination may be made as to whether the firstpredetermined period has lapsed before the realtor was successful inconsummating the proposed transaction associated with the lead record orscheduled appointment record subject of the offer record dispatched innstep 601. In the event that the realtor-client is unable to obtain asuccessful transaction from the lead record or scheduled appointmentrecord, the termination of the first predetermined period (for example,30 days) may trigger a re-categorization so that the lead record orscheduled appointment record may be re-categorized in step 604 below foran alternative use such as an alternative type of offer, or even asimilar offer, which may be provided to a second realtor-client.

In step 604, after the first predetermined time period associated withthe first record category has lapsed (for example after the 30 days),the system may categorize the record associated with the first offerrecord under a second category such as Tier II. This may includeassigning or receiving a second predetermined period associated with thesecond record category or lead tier II, and may include changing theoffer type. For example, an offer type ‘individual’ that may have beenpreviously associated with the offer record accepted by a firstrealtor-client who was unsuccessful, may then be re-categorized toinclude an offer type ‘market’ and offered to a second realtor-client.In exemplary embodiments, Tier II records may be displayed as a currenttop lead that may be sold at an early stage to a second realtor-clientat the top rate for the duration of the second predetermined period oftime applicable to Tier II records (for example, 7 days). Accordingly,offer records concerning lead records or scheduled appointment recordsin Tier II may be displayed via the GUI to other users at step 605, eventhough a lead record or a scheduled appointment record was originallyprovided to the first realtor-client that accepted the first offerrecord.

In step 606, a determination may be made as to whether the secondpredetermined period has lapsed. In the event that the secondrealtor-client is unable to obtain a successful transaction from thelead or scheduled appointment, a lapse of the second predeterminedperiod (for example, 7 days) may trigger a re-categorization so that thelead record or scheduled appointment record is categorized yet again.

In step 607, after the second predetermined period has lapsed, thesystem may categorize the lead record or scheduled appointment recordunder a third category such as Tier III. In exemplary embodiments, TierIII records may be instead displayed to a third realtor-client or evento several other realtor-clients; this may be achieved by providing theoffer record to multiple realtor-clients simultaneously. For example, inone embodiment, Tier III records may be made available to up to fivedifferent realtor-clients.

Accordingly, in step 608, an offer record in Tier III may be displayedvia the GUI to other realtor-clients.

It should be noted that in exemplary embodiments, every time a record ispurchased, the record is taken off from view of other realtor-clients.Further, every time a record is categorized (or a predetermined periodhas lapsed), the record may be returned to the service provider forreview and re-qualification. Furthermore, only three tiers or threecategories are shown as an example, but more or less categories may beimplemented without deviating from the scope of the present invention.

Turning now to the next figure, FIG. 7 illustrates a flowchart depictinga method for gathering information concerning leads, scheduledappointments, and other transactional opportunities, in accordance withpractice of one embodiment of the present invention. In an exemplaryembodiment, method 700 comprises: receiving or accessing a dispatchedappointment record (701); requesting a first update from arealtor-client concerning a Tier I record (702); displaying updateoptions via a GUI (703); receiving a realtor-client update concerningthe Tier I record (704); pushing notifications to the Tier Irealtor-client (705); requesting a second update from a realtor-clientconcerning a Tier II record (706); displaying update options via a GUI(707); receiving a realtor-client update concerning the Tier II record(708); and pushing notifications to the Tier II realtor-client (709).

To explain the steps above, method 700 concerns the interactions betweenthe system and the realtor-clients that purchase offer recordsassociated with lead records and scheduled appointment records. Althoughonly lead tiers I and II are discussed, this method may be implementedthroughout the life of a record in order to receive valuable feedbackfrom the realtor-clients that handle the leads and scheduledappointments.

In step 701, an offer record that has been dispatched or accepted by oneor more realtor-clients may be registered or confirmed as dispatched.

In step 702, a request from the service provider to the realtor-clientmay be provided via the GUI. For example, this may include providing aGUI that displays update options every time a predetermined period isinitiated at the outset of a lead tier (such as tier I). As will bediscussed below with reference to an exemplary GUI, this may be achievedby providing banners, messages, or menus that request for user feedbackfrom each realtor-client.

In step 703, accordingly, a GUI may display one or more options thatrequest information or feedback from the user. For example, see FIG. 18and FIG. 19.

In step 704, the user feedback may be received, stored, and analyzed.This information may be useful at a later time to better match therealtor-client with other potential offer records including leads andscheduled appointments for which the realtor-client may have a highprobability of success. Furthermore, in step 705, useful tips andinformation may be offered to the realtor-client currently handling thelead.

In step 706, further updates may be requested from the same or otherrealtor-clients that are currently handling the same or alternativeoffer record concerning the same lead, which is now in its secondpredetermined period or lead tier II.

Similarly, in step 707, a GUI may display one or more options thatrequest information or feedback from the realtor-client(s); and in step708, the user feedback may be received, stored, and analyzed. Again,these continuous updates concerning the development of the same lead maybe useful for optimizing the system. Furthermore, in step 709,additional useful tips and information may be offered to therealtor-client currently handling the lead.

FIG. 8 illustrates another method for gathering user data associatedwith the transacting of scheduled appointment records, in accordancewith practice of one embodiment the present invention. In exemplaryembodiments, the system may be configured to retrieve as much usefulinformation from its users as possible in order to better match userswith interested parties and generate new leads. This way, the system canbe configured to optimize itself by continuously learning from its usersabout their experiences. To these ends, method 800 describes one methodthat may be implemented with a system in accordance with the presentinvention. It is noted that although method 600 is shown in a particularsequence of steps, other conceivable sequence of the steps may bepracticed without deviating from the scope of the present invention.

In step 801, an acceptance of a lead record or scheduled appointmentrecord may be confirmed or received by the system. This may includereceiving confirmation that an offer has been accepted and an offerrecord concerning a lead or scheduled appointment record has beenpurchased or assigned to a particular realtor-client.

In step 802, specific events or actions taken by the user assigned to aparticular scheduled appointment record may be detected. For example,and without limiting the scope of the present invention, the system maydetect different calls to action such as initiating a call 802 a sendingan email correspondence 802 b, setting a reminder for a particular task802 c, executing an information pulling function 802 d, or any otheraction taken by the realtor-client for the purpose of furthering effortsto consummate a transaction opportunity associated with the scheduledappointment. Detecting these actions from a realtor-client may behelpful to track the realtor-client's progress, but also offer a uniqueopportunity to aid the realtor-client with suggestions or guidance, aswell as obtain information pertaining to feedback from therealtor-client's experience.

A call 802 a may be any call that is initiated by therealtor-client—this may include a call from the realtor-client to theinterested party to introduce themselves and verbally confirm theappointment date. This may be detected by the GUI in several ways. Inone embodiment, the user interface offers a means to initiate the callso that the action may be recorded. In other embodiments, the userinterface may request the realtor-client to indicate whether the initialcall was made.

An email correspondence 802 b may be any email that is initiated by therealtor-client—this may include sending an initial or follow-up emailcorrespondence from the realtor-client to the interested party. This maybe detected by the GUI in several ways. In one embodiment, the userinterface provides a means to initiate the email so that the action maybe recorded. In other embodiments, the user interface may request therealtor-client to indicate whether the email was sent.

Setting a reminder 802 c may be any reminder that the realtor-clientsets and which is associated with a task concerning the scheduledappointment record—this may include a reminder to follow-up with anothercall, a reminder for a follow-up meeting, or even the initial reminderfor the initial meeting subject of the scheduled appointment record.This may be detected by the GUI in several ways. In one embodiment, theuser interface provides a reminder function which may be associated witheach record and may be recorded. In other embodiments, the userinterface may request the realtor-client to indicate whether thereminder was set.

An information retrieval function 802 d may be any information gatheringtechnique, such as database searches, that may be implemented by therealtor-client—this may include accessing multi-listing services andpulling or retrieving data such as comparative market analysis data.These actions may be detected by the GUI in several ways. In oneembodiment, the user interface offers a means to initiate such functionsand thus the action may be recorded. In other embodiments, the userinterface may request the realtor-client to indicate whether theinformation was retrieved.

Naturally, other actions that may be expected or helpful to eachrealtor-client may be tracked in a similar manner.

In step 803, upon detecting or confirming that a particular action hasbeen taken by the realtor-client, a request for feedback from therealtor-client may be made. For example, a simple rating request may beprovided so that the realtor-client rates their experience.Additionally, specific questions geared towards a particular call ofaction may be provided to each realtor-client. Furthermore, commentsfrom the realtor-client may be requested to obtain more specificinformation. One example of a user interface is provided in FIG. 19below, which may be used to gather information from each realtor-clientat step 803. This way, the system may be configured to retrieve as muchuseful information from its realtor-clients as possible in order tobetter match realtor-clients with interested parties and generate newleads.

Turning now to FIG. 9, a method for distributing scheduled appointmentrecords or leads via a user interface on a client device, in accordancewith practice of one embodiment of the present invention, is discussed.More specifically, method 900 depicts one embodiment of how a scheduledappointment record may be offered to a realtor-client via a clientdevice that includes a mobile application in accordance with the presentinvention. As noted with other methods, the steps and particularsequence of steps in method 900 is only illustrative, and othersequences may be possible without deviating from the scope of thepresent invention.

In step 901, the system may notify the realtor-client of an existingoffer associated with a scheduled appointment record. Because therealtor-client has previously installed a mobile application provided bythe service provider, the realtor-client may or may not have enabledpush notifications. Accordingly, a client device with enabled pushnotifications may receive a notification alerting the realtor-client ofthe offer at step 902. If this is the case, notifications or alertscreens associated with the offer may be configured to automaticallylaunch the mobile application at step 903 using well known techniques.

Alternatively, a realtor-client may be required to manually launch themobile application (903), which may be configured to provide an alert, abadge, a banner, or any other known indicator that notifies therealtor-client of the pending offer.

At step 904, a determination confirms a login status of therealtor-client. If the realtor-client is already signed in, the offermay be provided via the GUI at step 906. If the realtor-client is notlogged in, or is their first time logging in to the mobile application,then one or more authentication protocols may be initiated at step 905.For example, this may typically require username, password creation, andprofile information input. In some embodiments, the service provider mayuse this step to associate the realtor-client to their membership classor membership type (or assign a role ID), which may have already beenestablished prior to signing up on the mobile application. Accordingly,each realtor-client may be provided with a set of privileges or accesspermissions that depend on the membership class or status of therealtor-client and which are associated with a role ID.

In step 906, the offer record may be provided including a predeterminedtime period to accept the offer record. In some embodiments,determinations at steps 907 and 908 may provide a time frame duringwhich to accept the offer record, decline the offer record, or timeframe to reconsider whether to decline (e.g. see FIG. 21). If the offerrecord is accepted, the scheduled appointment record may be fullydisclosed in step 910. If the offer is declined, then at step 909 therealtor-client may be guided to a main hub of the mobile application,such as a view of their current lead list.

In step 909, where the realtor-client declines the offer record, a listof current and or past leads and scheduled appointment records may beprovided via the GUI. Furthermore, declining an offer record may takethe realtor-client to a main hub or navigational options typicallyavailable via the GUI so that the realtor-client may easily engage withcurrently active leads and or other features, services offered via theGUI (e.g. see FIG. 15).

Alternatively, in step 910 the lead record or scheduled appointmentrecord—or all information associated with each record—may be fullydisclosed (e.g. see FIG. 16), providing all information required by therealtor-client to initiate contact with the interested party, confirmthe scheduled appointment on the scheduled appointment record (if ascheduled appointment record was purchased or accepted), and generallybegin taking the necessary actions to successfully close on thetransactional opportunity.

As will be explained further below with reference to specific examplesof the user interface, once a realtor-client is viewing a currentrecord—such as a newly accepted scheduled appointment record (910), or apreviously accepted appointment record (911)—several options will becomeavailable to the realtor-client. One such function may include settingreminders associated with each record (for example at steps 910 a or 911a). As explained above, this may include setting a reminder for aparticular task such as an initial call or simply a reminder for apending scheduled appointment or follow-up meeting.

Other useful functions may include running a conflict check to remind oralert the realtor-client of potentially conflicting meetings or eventsfor which the realtor-client has already set aside times. Accordingly,at step 912, a conflict check may be triggered and the GUI may display awarning banner, notification indicator, or other indicating objects viathe GUI to alert the realtor-client to check of a potential conflict(e.g. see FIG. 16, FIG. 18).

By step 913, a realtor-client typically has access to several calls ofaction or functions that enable the realtor-client to move towardssuccessfully closing the transactional opportunity. For example, step913 may include facilitating a call, email, or other correspondence, orfacilitating information retrieval.

In step 914, any action that was taken by the realtor-client may befollowed-up with a request for feedback (e.g. see FIG. 19).

The remaining figures disclose an exemplary GUI for facilitating thetransacting of scheduled appointments or leads. The figures show severalembodiments. For example, FIG. 10-FIG. 24 illustrate several embodimentsof a GUI, which may be provided via a mobile device application; thesefigures are discussed in turn.

FIG. 10 illustrates an exemplary dashboard for a GUI configured fortransacting lead records or scheduled appointment records, in accordancewith one embodiment of the present invention. The idea for the dashboardis to create a landing “friendly” and simple “call for action” page withwindows and buttons. The main windows may serve as a landing page ormain control page that offers a gateway to menus or sub-menus. Morespecifically, FIG. 10 illustrates client device 1000 which may be amobile device or smartphone. Naturally, client device 1000 may be adesktop computer, a tablet, a smartphone, or any other device suitablefor running a GUI such as a desktop application, a mobile application, abrowser suitable for accessing a website, or any other suitable softwarefor accessing a GUI in accordance with the present invention.

Typically, client device 1000 runs a GUI that includes a touch-screeninterface 1001, which may display a start-screen, landing page ordashboard. In such exemplary embodiment, the GUI may provide variousdata objects such as tabs, buttons, or navigation tools 1002, 1003,1004, 1005, and 1006.

Button 1002 is titled (as shown) “Find My Next Leads” and may enablevarious functions and tools for a realtor-client to identify potentiallead records or scheduled appointment records. Button 1003 is titles (asshown) “Manage My Social” and may enable various functions and tools fora realtor-client to manage posts, newsfeeds, and other social mediatools available via the GUI. Button 1004 is titles (as shown) “Manage MyLeads” and may enable various functions and tools for a realtor-clientto manage currently and previously active leads that have been purchasedor accepted, or are otherwise available via the GUI. Button 1005 istitles (as shown) “My Rankings” and may enable various functions andtools for a realtor-client to manage their progress with respect totheir active leads. Button 1006 may provide access to a profile page fora realtor-client to manage and update their profile available via theGUI.

FIG. 11 illustrates an exemplary location-based user interface forproviding client devices with available scheduled appointment records ortransaction opportunities, in accordance with one embodiment of thepresent invention. A realtor-client may navigate to this screen via thebutton 1002 which may enable find, search, sort and filter options toaid a realtor-client in selecting their next lead or scheduledappointment record.

In the illustrated embodiment, the GUI provides search function 1007 forsearching a particular geographic region, and may include filterfunction 1008 a (e.g. see also FIG. 12) or an onscreen filter function1008 to aid the realtor-client's search. Other features that may beimplementing using known techniques include reminder function 1009,navigational functions 1010 and 1011, and a “do you feel lucky” function1011 a.

Navigational function 1011 may include a menu or (as shown) anavigational pane that provides a type of site map for the GUI. Fromthis navigation tool a realtor-client may typically access all the mostoften used features provided by the GUI such as those presented at thelanding page or dashboard. Of course, other means of navigation may beimplemented without deviating from the scope of the present invention.

In an exemplary embodiment (as shown) a map layout may be provided,which shows several transactional opportunities that may comprisequalified leads or scheduled appointment records offered to therealtor-client.

In exemplary embodiments, only the types of records available to arealtor-client under a previously existing membership agreement will bedisplayed. This may be useful to ensure that each realtor-client onlyreceives targeted qualified leads or scheduled appointment records thatthey are qualified to accept.

In exemplary embodiments, different color coded indicators may beprovided to indicate important characteristics of each record. Forexample, and without limiting the scope of the present invention, Tier Irecords comprising scheduled appointment records provided exclusively tothe realtor-client may be color coded red, Tier II records comprisingqualified leads offered to a select or limited set of realtor-clientsmay be color coded yellow, and Tier III records comprising qualifiedlead records offered to all users may be color coded green. Of course,other means of providing this information may be practiced withoutdeviating from the scope of the present invention, including usingshapes, numbers, or any other types of identifiers to indicate the leadtiers or category of a particular offer record.

In the present embodiment, record 1012 may represent a Tier II record,record 1013 may represent a Tier II record, and record 1014 mayrepresent a Tier I record. Selecting one of the availableproperties/scheduled appointments or transaction opportunities presentedvia this screen may lead to the screen illustrated by FIG. 13.Alternatively, selecting filter function 1008 a may lead to the screenillustrated by FIG. 12 and discussed in turn.

FIG. 12 illustrates an exemplary management tool for assistingrealtor-clients with transacting scheduled appointment records, inaccordance with one embodiment of the present invention. For example,filters may be implemented to allow a realtor-client to select what typeof transaction opportunities are displayed for that realtor-client. Asmentioned above, scheduled appointment records may be categorized indifferent ways to maximize and monitor each transactional opportunity.Via an exemplary interface such as the one illustrated, realtor-clientsmay be allowed to glean or even search exclusively for a particularcategory of transactional opportunities.

Tools that may be made available to realtor-clients via this interfaceor filter function 1008 a may include, without limitation: enabling ordisabling a view of one or more Tiers of records (tool 1015); selectinga price range tool 1016; selecting a square footage tool 1017; a bedroomselection tool 1018; a bathroom selection tool 1019; and any otherselection tools that help a realtor-client narrow or broaden a searchfor a particular type of lead or property.

FIG. 13 illustrates an exemplary user interface, in which some of thedetails of a particular transactional opportunity may be displayed. Thedisplayed information may include photographs, pricing information,contact information, property information, and an interface forpurchasing or auctioning the transactional opportunity. Typically, theshown screen comprises the preview information associated with a leadrecord or scheduled appointment record and which is provided as an offerrecord for a realtor-client to purchase or accept, bin on, or decline.More specifically, offer record 1300 is shown.

Offer record 1300 may include image 1020, pricing information 1021,additional information 1022, property information 1023 and 1024, acceptbutton 1025, decline button 1026, bid button 1027, and contact button1028. While different embodiments may include more or less informationthan shown in offer 1300, typically specific information such as thename of the interested party or address of the property may be excludedor blurred out until after purchase or acceptance of the record.Similarly, contact button 1028 may be disabled prior to purchase. Thismay be desirable so that the realtor-client must accept the offer recordprior to being able to contact the interested party.

As mentioned above, some offer records (particularly those involvingscheduled appointment records rather than qualified lead records) may betime-sensitive and thus include a predetermined allotted time for therealtor-client to accept or decline. Accordingly, offer 1300 may furtherinclude a timer or similar feature that informs the realtor-client ofthe remaining time under which to accept the offer before being offeredto another set of one or more realtor-clients. An exemplary embodimentof such offer record is illustrated in the next figure.

FIG. 14 illustrates an exemplary interface for providing atime-sensitive offer record associated with a scheduled appointmentrecord. More specifically, offer record 1400 is shown, including timer1029. In exemplary embodiments, the system may use the time ofacceptance of the offer record and a time limitation associated withscheduled appointment record in order to generate an active time limiton the offer. In exemplary embodiments, this may include providing anoffer record that includes a timer, or a notification may be sent to arealtor-client via client device, which includes a timer. By way of anon-limiting example, notice 1029, which includes a timer may beprovided with offer record 1400.

FIG. 15 illustrates an exemplary management tool for assistingrealtor-clients with managing their purchased leads or purchasedscheduled appointment records, in accordance with one embodiment of thepresent invention. Moreover, selecting “MANAGE MY LEADS” from thedashboard may guide the realtor-client to this screen. The idea is forthe realtor-clients to be able to view all the lists of prior acceptedleads and even upload their own. As such, the main landing page may bethe list as shown FIG. 15 with a flow to the CRM client page thatincludes all reminders, calendars, email, text and management functions.In the embodiment shown, several tools may be provided including toggletool 1030 for switching between viewing active and past leads, as wellas a search tool 1031 for searching through a realtor-client's leads.

FIG. 16 illustrates an exemplary interface for facilitating themanagement of purchased scheduled appointment records, in accordancewith one embodiment of the present invention. More specifically, FIG. 16illustrates a scheduled appointment record or record 1600. Typically,record 1600 includes all the information provided in offer 1300 and anyinformation withheld in the offer, such as specific property informationincluding address of the property, as well as the name and contactinformation of the interested party. Other features may be enabled orpresent for the first time, such as a means to contact the interestedparty as well as other useful tools including a reminder setting tool.As such, record 1600 may include contact button 1034 and set reminderbutton 1035 to enable said functionalities.

Additionally, other functionalities or tools may include indicators 1032and 1033. These may be objects such as banners, labels, or buttons, thatalert and inform the realtor-client of important relevant informationsuch as an upcoming time associated with record 1600, or a timeassociated with another record conflicting with record 1600. Using wellknown techniques, indicators 1032 and 1033 may enable other functions orviews that further aid the realtor-client in managing their otherrecords.

In one embodiment, indicator 1032 may display a remaining time until thenext meeting the realtor-client has previously scheduled. As such,clicking on indicator 1032 may retrieve information pertaining to thatrecord. In another embodiment, indicator 1032 may simply display aremaining time until the next meeting associated with record 1600.

In one embodiment, indicator 1033 may display a message concerningpotentially conflicting meeting. As such, clicking on indicator 1033 mayretrieve a list pertaining to records that include potentiallyconflicting meeting times. In another embodiment, indicator 1032 maysimply display a conflict associated with record 1600, only if there isindeed a potential conflict with record 1600.

As may be apparent, other embodiments and variations may be possiblewithout deviating from the scope of the present invention.

Activating link or set reminder button 1035 may enable a set reminderfunction as explained above. FIG. 17 exemplarily illustrates suchfeature, in one possible embodiment of a GUI that provides for suchfeature. As shown, reminder function 1035 a facilitates commonly usedreminders within the GUI. As mentioned above, enabling functions via theGUI may aid the service provider in tracking realtor-client actions.This in turn aids the realtor-client by allowing the service provider tofollow-up with suggestions, guidance, and other assistance that maybenefit the realtor-client.

To these ends, record 1600 may further include indicator 1036, which maycomprise objects such as banners, labels, or buttons that alert andrequest feedback from the realtor-client. Accordingly, FIG. 18illustrates another exemplary interface for facilitating the managementof purchased scheduled appointment records, in accordance with oneembodiment of the present invention. More specifically, FIG. 18 showsrecord 1600 which includes indicator 1036. Indicator 1036 may beprovided after detecting that one or more actions by the realtor-clienthave taken place—for example as explained with reference to method 800.

In the shown embodiment, indicator 1036 includes a message that states“LET US KNOW HOW IT WENT” with a clickable object that may retrieve alist of questions, a comment box, or link the realtor-client to adifferent screen (e.g. see FIG. 19) where the service provider mayrequest information about a particular event, action, or step that therealtor-client has taken towards closing the transactional opportunity.As may be apparent, other embodiments and variations may be possible anddifferent means of obtaining feedback from a realtor-client may beimplemented without deviating from the scope of the present invention.

FIG. 19 illustrates an exemplary interface for requesting realtor-clientdata associated with one or more transactions of scheduled appointmentrecords. More specifically, FIG. 19 depicts feedback form 1900, whichmany include requests for various types of information associated with arealtor-client's experience during a particular call for action. Theserequests may include a request to rate performance, a request to ratethe realtor-client's experience, a request for comments or notes, arequest with specific questions for specific information, or any otherrequest for information that the service provider may be interested in.In the shown embodiment, feedback form 1900 includes rate box 1036 a(with a plurality of questions and statements that the realtor-client isrequested to rate from a scale of one through five), and comment box1037 for the realtor-client to input notes or comments via text.

Examples of how this feedback may be utilized by the service providerincludes facilitating more successfully matches between thatrealtor-client with future qualified leads and scheduled appointments;facilitating more compatible matches between that realtor-client withfuture interested parties; providing the realtor-client with feedback toimprove future interactions and success in future transactionalopportunities; and overall optimize the system to better assistrealtor-clients and maximize revenue stream.

FIG. 20 illustrates an exemplary user interface configured to providenotifications concerning available transaction opportunities, inaccordance with one embodiment of the present invention. For example,notification such as those discussed with reference to method 600 may beprovided in this screen.

FIG. 21 illustrates another exemplary screen that may be provided to auser for feedback upon declining an offer. This information may aid theservice provider by providing information that allows the serviceprovider to learn about the particular realtor-client preferences sothat future offers are better matched. Similarly, the service providermay obtain information pertaining to the property, the pricing of theoffer, or any other details that may guide the service provider inoptimization of the system.

FIG. 22 illustrates another exemplary embodiment of a record that hasbeen purchased or accepted by a realtor-client. As with record 1600, allpertinent information regarding the qualified lead or scheduledappointment may be provided. Additionally, different functions may beimplemented such the call and email launching functions mentioned above.In the embodiment shown an interface for communicating with theinterested party is also included with the GUI; again this may behelpful for the service provider to track actions taken by therealtor-client (although not necessarily the contents of thecommunication).

FIG. 23 illustrates an exemplary social media platform provided via theuser interface, in accordance with one embodiment of the presentinvention. A realtor-client may access this screen by selecting “MANAGEMY SOCIAL” from the dashboard. Post, manage and send listings to allsocial sites can be enabled from this screen. These functionalities mayfacilitate realtor-clients to view their prior posts/currently on theirsocial sites, and even research trending articles.

Finally, FIG. 24 illustrates an exemplary user interface, whichimplements an incentive-based algorithm, in accordance with oneembodiment of the present invention. A realtor-client may access thisscreen by selecting “MY RANKINGS” from the dashboard. In exemplaryembodiments, the incentive-based algorithm may provide incentives suchas earning credit and ranking by using the mobile application. The ideais to engage the realtor-client, develop best practices and providerewards or incentives for data sharing and proactive realtor management.Moreover, data provided by realtor-clients can be recycled or utilizedby the service provider—effectively utilizing clients of the system asan additional source of data, which may be in turn provided back torealtor-clients to take advantage of the transactional opportunitiesgenerated from that data.

Although the transactional opportunities that the system described abovefocus on real estate transactions, other applications in other fieldsmay just as easily be implemented. For example, and without deviatingfrom the scope of the present invention, a system and method such as theone described above may be practice with respect to mortgages,contractors, inspection services, or other fields in which scheduledappointments are key to consummating a transaction.

A system and method for transacting scheduled appointments has beendescribed. The foregoing description of the various exemplaryembodiments of the invention has been presented for the purposes ofillustration and disclosure. It is not intended to be exhaustive or tolimit the invention to the precise form disclosed. Many modificationsand variations are possible in light of the above teaching withoutdeparting from the spirit of the invention.

What is claimed is:
 1. A system for transacting a scheduled appointmentrecord, comprising: a server; a database accessible by the server; and acontrol module configured for: receiving lead information via a dataaggregation website in communication with the server; generating anoffer record based on the lead information; assigning the offer recordto a realtor-client; determining whether an agreement concerning aproposed transaction has been secured; and either: rehashing the offerrecord if an agreement was not secured, or registering with therealtor-client the consummation of the proposed transaction.
 2. Thesystem of claim 1, wherein the offer record comprises: a scheduledappointment record associated with a previously scheduled meeting at aspecific date and a specific time agreed-to by an interested party todiscuss the proposed transaction with at least one user of the dataaggregation website.
 3. The system of claim 1, wherein the scheduledappointment record comprises: a lead price for the offer record isestablished based on a value of a prospect for consummating the proposedtransaction.
 4. The system of claim 1, wherein the data aggregationwebsite is configured for: displaying a map layout including one or moreindicators associated with one or more offer records offered to one ormore realtor-clients.
 5. The system of claim 1, wherein the leadinformation includes a lead ID for identifying and keeping track of alead record.
 6. The system of claim 1, wherein the lead informationincludes a property ID for identifying or referencing real property thatis subject of the offer record.
 7. The system of claim 6, wherein thelead information includes an owner ID for identifying an ownerassociated with the property ID.
 8. The system of claim 1, wherein thelead information includes a source ID for identifying a source of thelead information.
 9. The system of claim 1, wherein the lead informationincludes a CRM ID for aggregate reporting purposes.
 10. The system ofclaim 1, wherein the lead information includes a lead type indicator foridentifying a type of lead including a lead for a potential sale or alead for a potential buy.
 11. The system of claim 1, wherein the leadinformation includes a lead tier for indicating a lead categoryaccording to a protocol for managing lead records and scheduledappointment records.
 12. The system of claim 1, wherein the leadinformation includes a lead price for designating a predetermined pricefor the record.
 13. The system of claim 1, wherein the lead informationincludes dispatch information concerning comments or useful informationthat may help sell the lead.
 14. The system of claim 1, wherein the leadinformation includes a lead status that provides an indicator forkeeping track of whether a lead record is active, has been sold, or isno longer available for generating the offer record.
 15. A method,performed by a server configured for transacting a scheduled appointmentrecord, comprising: receiving lead information via a data aggregationwebsite in communication with the server; generating an offer recordbased on the lead information; assigning the offer record to arealtor-client, wherein the offer record comprises a scheduledappointment record associated with a previously scheduled meeting at aspecific date and a specific time agreed-to by an interested party todiscuss a proposed transaction with at least one user of the dataaggregation website; determining whether an agreement concerning theproposed transaction has been secured; and either: rehashing the offerrecord if an agreement was not secured, or registering with therealtor-client the consummation of the proposed transaction.
 16. Themethod of claim 15, further comprising: generating a lead ID foridentifying and keeping track of a lead record.
 17. The method of claim15, further comprising: generating a property ID for identifying realproperty that is subject of the offer record.
 18. The method of claim15, further comprising: generating an owner ID for identifying an ownerassociated with the property ID.
 19. The method of claim 15, furthercomprising: generating a source ID for identifying a source of the leadinformation.
 20. The method of claim 15, further comprising: generatinga CRM ID for aggregate reporting purposes.